Safe printing

ABSTRACT

Approaches for processing a digital file in a manner designed to minimize exposure of any malicious code contained therein. A digital file resides with a virtual machine. When the virtual machine receives an instruction to print or digitally transfer at least a portion of the digital file, the virtual machine converts at least a portion of the digital file from an original format to a different format within the virtual machine. The different format preserves a visual presentation of the digital file without supporting metadata or file format data structures of the original format. The virtual machine instructs the host OS to print or digitally transfer the portion of the digital file. The host OS may consult policy data in determining how to service the instruction to print or digitally transfer the digital file.

CLAIM OF PRIORITY

This application is a continuation-in-part of, and claims priority to, U.S. patent application Ser. No. 13/526,810, filed on Jun. 19, 2012, entitled “Safe Printing,” invented by Deepak Khajuria et al., the disclosure of which is hereby incorporated by reference in its entirety for all purposes as if fully set forth herein.

U.S. patent application Ser. No. 13/526,810 is a continuation-in-part of, and claims priority to, U.S. patent application Ser. No. 13/419,356, filed on Mar. 13, 2012, entitled “Securing File Trust with File Format Conversions,” invented by Gaurav Banga et al., the disclosure of which is hereby incorporated by reference in its entirety for all purposes as if fully set forth herein.

FIELD OF THE INVENTION

Embodiments of the invention relate to processing a file, which may potentially contain malicious code, in a safe manner.

BACKGROUND

Ensuring the security of Internet users and Internet connected devices is one of the grand challenges facing us today. The current state of affairs is very problematic, as our cyber-security infrastructure is easily and routinely subverted by cyber criminals, resulting in great economic loss. Every year brings deeper and more complex dependence by society on our cyber-infrastructure, and yet at the same time the cyber-security problem only worsens as the capabilities of the cyber-criminal mature. In effect, we are building mission-critical dependence into virtually every aspect of human activities on a cyber-infrastructure that is very insecure at its core.

The prevailing school of thought on how to protect cyber-infrastructures places great emphasis on the detection of security vulnerabilities to anticipate how an attack will take place. Once a vulnerability is detected, countermeasures are enacted. This philosophy extends to how viruses and other potentially malicious digital files are handled. Presently, there are a variety of techniques for scanning digital files to determine whether any portion of the digital file matches a signature associated with a known virus or malicious code. Once identified, such dangerous files are quarantined and appropriate security measures taken. Unfortunately, due to an increase in exploitation of file format vulnerabilities, attacks that exploit relatively unknown vulnerabilities are becoming more common.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:

FIG. 1 is a flowchart illustrating the functional steps of ensuring a digital file does not contain malicious code according to an embodiment of the invention;

FIG. 2 is a diagram of various locations within a computer network where the steps of FIG. 1 may be performed according to an embodiment of the invention;

FIG. 3 is an illustration of processing dynamic content within a digital file according to an embodiment of the invention;

FIG. 4 is an illustration of an original data file stored in association with a sterilized file according to an embodiment;

FIG. 5 is a block diagram that illustrates a computer system upon which an embodiment of the invention may be implemented; and

FIG. 6 is a flowchart illustrating the steps of printing a digital file safely according to an embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

Approaches for processing a digital file, which may contain malicious code, in a safe manner are presented herein. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the invention described herein. It will be apparent, however, that the embodiments of the invention described herein may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form or discussed at a high level in order to avoid unnecessarily obscuring teachings of embodiments of the invention.

Using File Format Conversion to Secure File Trust

Embodiments of the invention prevent the spread of malicious code using a fundamentally different paradigm than prior approaches. In the past, the security of a computer system or network rested upon ensuring that malicious code could be identified and subsequently contained. Rather than attempting to identify malicious code, embodiments assume that any digital file may potentially carry malicious code. Any digital file entering a secure area is processed to remove any malicious code carried therein, thereby allowing the digital file to be trusted within the secure area. After processing a digital file to ensure that any malicious code therein is removed, the digital file may be branded with a signature or the like so that the digital file's trustworthiness is verifiable to consumers of the digital file within an enterprise.

Embodiments of the invention operate under the observation that malicious code hiding within a digital file is designed to exploit file format vulnerabilities. For example, often malicious code is carried by a digital file that the user is tricked into opening. When such a file is opened, the code contained therein is allowed to execute, which opens the door for the malicious code to spread or otherwise achieve its nefarious objective. Embodiments of the invention remove any malicious code carried by a digital file by converting the digital file to a different file format so that any metadata or data structures of the original file format which may have carried the malicious code are removed. Converting the digital file to a different file format in this fashion still preserves how the digital file is visually and/or audibly perceived by a user.

FIG. 1 is a flowchart illustrating the functional steps of ensuring a digital file does not contain malicious code according to an embodiment of the invention. As shall be explained in further detail below, the steps of FIG. 1 may be performed on a digital file by a variety of different entities in a variety of different contexts. Generally speaking, the steps of FIG. 1 may be performed when a digital file enters a secure area (such as a computer network, a device, or domain) or when the digital file is selected or opened by any party, be it a user or a computerized entity.

In step 110 of FIG. 1, a copy (termed the “intermediate copy”) of an original digital file is created. The intermediate copy is in a different file format than the original digital file. The intermediate copy will represent the same type of content as the original digital file. For example, if the original digital file is a visual presentation, an audio presentation, or a video, then the intermediate copy will also be a visual presentation, an audio presentation, or a video respectively.

To provide a concrete example, if the original digital file is an Adobe Acrobat document (i.e., the digital file has a “.pdf” extension), then the intermediate copy may be a JPEG image file (i.e., the digital file has a “.jpeg” extension). Both an Adobe Acrobat document and a JPEG image file may be used to describe how to visually represent a document or image, but do so using different file formats. Thus, the same visual presentation may be represented as both an Adobe Acrobat document and a JPEG document. Similarly, if the original digital file is an audio presentation (such as a digital file with a “.mp3” extension) or in a video format (such as a digital file with a “.avi” extension), the intermediate copy will also be an audio presentation or in a video format respectively.

In an embodiment, in step 110 multiple intermediate files may be created to represent a single original digital file. To illustrate, assume that the original digital file in step 110 is a three page Adobe Acrobat document and further assume that the three page Adobe Acrobat document is to be converted into a JPEG intermediate file format in step 110. In performing step 110 in this example, the three page Adobe Acrobat document may be converted into a collection of JPEG files, each of which is an image corresponding to a different page of the Adobe Acrobat document.

In addition to the collection of JPEG files representing the pages of the Adobe Acrobat document, metadata information which contains a mapping of which JPEG file corresponds to which page of the original Adobe Acrobat document may also be created in step 110. This metadata information may be represented in a variety of different ways. This metadata information may reside in a separate file. Alternately, the metadata information may be a convention that employs the metadata capabilities of the file system itself. As an example, a five page Adobe Acrobat document called foo.PDF may be converted to a folder (or compressed folder file—foo.zip) which contains files foo_001.jpg, foo_002.jpg, . . . foo_005.jpg. Using this metadata information, one or more intermediate files created in step 110 may subsequently be combined together to form a single file, such as a JPEG image that has all the pages cascaded together into one gigantic image or a ZIP file containing a folder of all the JPEG image files created in step 110.

For clarity, examples and discussion will be presented herein as an intermediate copy being created in step 110. However, in view of the above discussion, those in the art shall recognize that one or more intermediate copies may be created in step 110 or a single intermediate copy created in step 110 may represent multiple files in the intermediate file format or the original file format in step 110.

The purpose of creating an intermediate copy in a different file format (referred to as the “intermediate format”) than the original file format is to preserve how the digital file is visually or audibly perceived when rendered or played in the intermediate format without the intermediate format supporting the metadata or file format data structures of the original file format. To illustrate using the above example involving an original format of a “.pdf” document and an intermediate format of a JPEG image, the intermediate copy expressed in a JPEG image file format should have the same visual appearance as the original Adobe Acrobat document, but the intermediate copy lacks the metadata and data structures inherent within the original Adobe Acrobat document. Thus, any malicious code contained within the original Adobe Acrobat document would not be carried forward into the intermediate copy expressed as a JPEG image, as such malicious code would be lost in translation.

It is noted that there would not necessarily be a reduction in resolution or quality between the original digital file and the intermediate copy. In fact, in many cases resolution and quality can actually be improved in the intermediate copy.

The particular intermediate format used should be the file format which provides the highest resolution and/or quality in the least amount of physical space. Naturally, there may be a correlation between the size of a digital file and its resolution and/or quality, and so an intermediate format should be selected for use in step 110 which satisfies both criteria to an acceptable level. Embodiments of the invention would enable a user to customize into which particular intermediate format each digital file format will be converted. In an embodiment, the particular intermediate format used should be one that is relatively simple (for example, the .JPEG image file format) such that the likelihood of a bug in software that handles the intermediate file format is low because the intermediate format employed is simple to parse.

An intermediate copy in an intermediate format may be created using a software conversion program that converts a digital file from one file format to another. In effect, such a conversion program serializes the original digital file into the intermediate format. Thus, the intermediate format may be a serialized representation of the digital file. Such conversion programs are generally available for all common file formats. The inventors note that propriety file formats can be supported by embodiments through the use of custom conversion programs. Accordingly, embodiments have no limits on the types of digital files which may be converted into or expressed as intermediate copies in step 110.

The creation of the intermediate file in step 110, as well as the creation of the sterilized file in step 120 explained in detail below, may be performed in the background in a manner transparent to the user. For example, the steps of FIG. 1 may be performed automatically (i.e., without the request or knowledge of the user) whenever a user clicks or selects a file, the user receives an email, or whenever the user receives a file from outside a trusted domain (such as anytime the user receives a file over the Internet). In this way, in certain embodiments, the user experience of embodiments should not deviate from the expected behavior of the user's system.

In step 120, a sterilized copy of the digital file is created from the intermediate copy. The sterilized copy is a copy of the intermediate file that has been converted back into the original file format.

Note that the performance of step 120 is optional, as certain embodiments may only perform step 110 and not perform step 120. To illustrate a use case where step 120 is not performed, if a user simply wishes to view a digital file using an application, then the user may not care in which digital file format the digital file is represented in, and step 120 need not be performed. The application can safely use the intermediate copy created in step 110 to render a visual presentation to display to the user.

However, the inventors anticipate that most embodiments will perform step 120, as the sterilized copy is in the same file format as the original digital file, which is the file format that the user expects to interact. Accordingly, to provide a seamless user experience and an extra assurance of protection, step 120 will typically be performed.

The performance of step 120 does provide an extra assurance of protection, as the conversion of the intermediate copy in the intermediate format into the sterilized copy in the original file format will also remove metadata and data structures inherent in the intermediate file format form the sterilized copy.

The sterilized copy may be created in step 120 using a similar software conversion program such as discussed above with reference to step 110. In effect, the conversion program in step 120 deserializes the intermediate copy into the sterilized copy in the original file format.

In an embodiment, the sterilized copy may comprise a digital signature indicating that the sterilized copy has been converted from the intermediate format to the original format. In this way, when the sterilized copy is shared across the organization, other recipients or consumers of the sterilized copy may determine that the sterilized copy can be trusted by verifying the presence of the digital signature within the sterilized copy. The digital signature may be implemented using a variety of different mechanisms. To illustrate an example, in the performance of step 120, a SHA-1 or MD5 hash of the sterilized copy or the original digital file may be inserted into the sterilized copy. As long as the sterilized copy is not edited after being branded with the digital signature, the sterilized copy may be considered “safe” and “trustworthy” by entities within an organization.

Embodiments May be Implemented in Numerous Ways

The steps of FIG. 1 may be performed by a variety of different entities and at a variety of different locations. To illustrate, consider FIG. 2, which is a diagram of various locations within a computer network where the steps of FIG. 1 may be performed according to an embodiment of the invention. The steps of FIG. 1 may be performed by any entity or device that is capable of buffering an entire digital file. The steps of FIG. 1 may be performed anytime a digital file enters trusted domain 210 or by any device within trusted domain 210. For example, anytime a digital file is retrieved from the Internet, edge router 220 may perform the steps of FIG. 1 on the digital file. Alternately, mail gateway 222 may perform the steps of FIG. 1 on any attachment to an email received by mail gateway 222. The steps of FIG. 1 can be implemented in any network inspection device, such as a mail gateway, or any other device capable of MIME decoding of email attachments and downloads.

The steps of FIG. 1 may also be performed by cloud service 230, which is a remote service accessible by devices within trusted domain 210. For example, a user may instruct wireless device 226 (which may be a tablet PC or cell phone) to contact cloud service 230 to request that cloud service 230 perform the steps of FIG. 1 on a set of one or more digital files identified by the user.

In an embodiment, the steps of FIG. 1 may be performed at PC 224 either automatically or in response to a variety of different user actions. To illustrate, in an embodiment, when a user selects a digital file (for example, via a right mouse click), the user may be presented with an option to choose whether he or she would like to execute the digital file within a virtual machine or perform the steps of FIG. 1 on the digital file before executing, rendering, or playing the digital file on the host operating system.

As the performance of step 110 of FIG. 1 may be prone to attack by malware (as this step converts a potentially malicious digital file into a safe file format), embodiments may perform step 110 and/or step 120 of FIG. 1 in a virtual machine created from a state known to be safe. After the performance of step 110 which produces a safe intermediate file, the safe intermediate file may be safely extracted from the temporary virtual machine and the temporary virtual machine may be discarded.

In an embodiment, the temporary virtual machines in which one or more of steps 110 and 120 of FIG. 1 are performed correspond to the UCVMs discussed in U.S. patent application Ser. No. 13/115,354, filed on May 25, 2011, entitled “Approaches for Securing an Internet Endpoint Using Fine-Grained Operating System Virtualization,” which is incorporated by reference for all purposes as if fully set forth herein. Additional discussion regarding the use of virtual machines with reference to the steps of FIG. 1 will be presented below in the section entitled “Implementation With Virtual Machines.”

Embodiments of the invention may perform the steps of FIG. 1 automatically (i.e., without receiving a user request or informing the user) in certain contexts. To illustrate, certain embodiments may automatically perform the steps of FIG. 1 on any digital file that is migrated from a virtualized environment to the desktop or a server. As another example, certain embodiments may automatically perform the steps of FIG. 1 on any attachment to an email client (like Microsoft Outlook) that is opened by a user.

The steps of FIG. 1 may also be performed by any software component within trusted domain 210 that interacts with a digital file which does not contain a digital signature indicating that it has previously been sterilized. For example, such a software component may correspond to software executing on an edge router, an email server, an email client, a web browser, or any software responsible for managing the instantiation and de-instantiation of one or more virtual machines. In an embodiment, a web browser may be configured with a plug-in which causes the web browser to perform the steps of FIG. 1 on any digital file downloaded from the Internet.

The steps of FIG. 1 may also be performed on a specialized custom hardware device, such as one that employs custom application specific integrated circuits (ASICs), to perform one or more of the steps of FIG. 1 without the use of any software.

Processing Digital Files that Contain Macros and Scripts

Certain digital files may contain dynamic content, such as a macro or a script. For example, an Excel spreadsheet may contain an embedded Visual Basic (VB) script. Embodiments of the invention may be designed to analyze such dynamic content to determine if it is safe, and may include any dynamic deemed safe in the sterilized copy created in step 120. FIG. 3 is an illustration of processing dynamic content within a digital file according to an embodiment of the invention. While FIG. 3 makes reference to the dynamic content being a macro, the techniques discussed herein may be applied for use with any type of dynamic content.

As depicted in FIG. 3, a macro is removed from the digital file in the original format in step 210. The macro may be examined to determine whether the macro conforms to one or more rules. The purpose of the one or more rules is to ensure that only dynamic content deemed safe is migrated to the sterilized copy in step 120. Dynamic content that is deemed safe (i.e., no malicious or problematic content is contained therein) may be inserted into the sterilized copy created in step 120. As shall be explained in further detail below, actions performed in the performance of processing dynamic content to ensure that it is safe and migrating the safe dynamic content into the sterilized copy in step 120 may be, but need not be, performed in a virtual machine or in a UCVM.

In embodiments, the processing of dynamic content within a digital file to ensure that the dynamic content is deemed safe may only be possible when the intermediate format is such that the sterilized dynamic content may be properly combined with the sterilized file in step 120. For example, to assist the combination of the sterilized dynamic content and the sterilized file, a digital file with a .doc extension may need to be converted into a .doc which has all macros removed by a special convertor, and thereafter any macros deemed safe may be added to the sanitized copy of the digital file.

The one or more rules used to examine dynamic content may be arbitrarily complex. An example of a rule is that macros are permissible as long as they are not named as a function. Another example of a rule is that no linked files are allowed.

Rules can be used to disable problematic features. For example, there may be a certain feature that represents a security issue, and any digital file is deemed untrustworthy if in possession of this feature. A rule could be designed to remove the problematic feature from the dynamic content so that the remainder of the dynamic content may be migrated to the sterilized copy in step 120 without the problematic feature. In this way, a digital file can have the problematic feature and be considered untrustworthy or may have the problematic feature removed to be considered trustworthy.

As another example, a rule could be designed such that only sterilized copies of digital files are considered trustworthy. Alternately or additionally, a rule could state that only certain types of files (such as spreadsheets) need be processed using the steps of FIG. 1 to be considered trustworthy. A rule may also state what type of intermediate format a particular file format should be converted into in step 110. For example, a rule could state that all image files should be converted into a “.png” file format and be considered trustworthy, but that a digital file in the “.jpeg” file format should not be trusted.

If a portion of a macro is identified which does not conform to a rule, that portion of the macro may be revised to conform the macro to the rule to produce a sterilized macro. For example, if the name of a macro does not conform to a rule, then the name of the macro may be revised in accordance with the rule, and the revised macro may be inserted back into the sterilized copy in step 120.

In an alternate embodiment, after determining that the macro does not conform to a rule, the macro may not be inserted into the sterilized copy in step 120, thereby causing the macro to be removed from the sterilized copy.

The rules discussed herein in this section may be used in conjunction with or correspond to those policies discussed in U.S. patent application Ser. No. 13/419,345, entitled “Seamless Management of Untrusted Data Using Virtual Machines,” filed on Mar. 13, 2012, invented by Gaurav Banga et al., the contents of which are hereby incorporated by reference for all purposes as if fully set forth herein.

Maintaining the Original and Sterilized File within a File System

After the performance of the steps of FIG. 1, the original digital file in the original format may be maintained in association with the sterilized copy of the digital file. For example, if a user stores a copy of the sterilized copy of the digital file in a folder of a file system, then the original digital file may also be stored in the same folder. This is so as to accommodate the performance of a merge-edit operation, which will be discussed below. In an embodiment, the original digital file and the sterilized copy of the digital file may be stored together, and perhaps may be organized as a tuple.

To illustrate, consider FIG. 4, which is an illustration of original data file stored 410 in association with sterilized file 420 according to an embodiment. As depicted in FIG. 4, both original data file 410 and sterilized file 420 are stored in folder 402 of a file system. Original file 410 is depicted in a dotted line in FIG. 4 because original file 401 may have a hidden attribute which prevents original data file 410 from being viewed by a user. Thus, a user visually inspecting the contents of folder 402 would see sterilized copy 420 but may not see original file 410.

Original file 410 and sterilized copy 420 operate as linked files in that an operation performed on one of them is performed against both. For example, if a user performs a move operation on sterilized copy 420 to move sterilized copy 420 to a different location within the file system, the move operation is also automatically and transparently performed on original file 410 so that the association between sterilized copy 420 and original file 410 may be maintained. As another example, if a user attaches sterilized copy 420 to an email, then original file 410 may also become attached to the email. There are a variety of different ways to implement this behavior. For example, both sterilized copy 420 and original file 410 may be organized as a tuple and both files may separately be attached to the email. Alternatively, both sterilized copy 420 and original file 410 may be organized within and stored as a single data structure, such as a blob, and the single data structure may be attached to the email.

Performing a Merge-Edit Operation

Embodiments of the invention support the performance of a merge-edit operation. A merge-edit operation is an operation where all or a portion of a first file is embedded or copied into a second file, where the metadata and the file format data structures of the first file are copied into the second file as well. For example, assume an Excel spreadsheet contains a macro. If you wish to copy the Excel spreadsheet, along with the macro, into another document, you may do so using a merge-edit. However, if you only want to insert data or a portion of the display of the Excel spreadsheet without coping the macro or other metadata/data structures of the Excel spreadsheet, then a normal edit operation may be performed to do so.

To perform a merge-edit operation, it is necessary to have a version of a digital file that contains a high fidelity version of the metadata, file format data structures, and dynamic content of the original digital file. Therefore, as explained above, certain embodiments of the inventions may store, in association with a sterilized copy of a digital file, the original data file as well. In this way, if a merge-edit operation is desired to be performed, the merge-edit operation may be performed using the original data file which accompanies the sterilized file. Note that the presence of the original data file may be hidden from the user, and so the user requesting a merge-edit operation may be unaware that the merge-edit operation is actually performed using the original data filed stored in association with the sterilized copy.

A merge-edit operation may involve untrusted data, and as such, should be treated as an untrusted operation. As a result, in an embodiment, all merge-edit operations are ideally performed in a virtual machine or in a UCVM. Additional discussion on how this may be performed is provided in the next section.

Implementation with Virtual Machines

Embodiments of the invention may, but need not, perform one or more steps of FIG. 1 within a virtual machine. Step 110 may be performed in a virtual machine that is instantiated immediately prior to and for the purpose of the creation of the intermediate copy. The creation of the sterilized copy in step 120 may be performed within another virtual machine that is instantiated immediately prior to and for the purpose of the creation of the sterilized copy. Alternately, the creation of the sterilized copy in step 120 may be performed within the host operating system outside of any virtual machine.

Note that after the performance of step 120 of FIG. 1, the sterilized copy may be stored in a file system provided by the host operating system, and any virtual machine instantiated for the purpose of creating the intermediate copy in step 110 or the sterilized copy in step 120 may be de-instantiated.

In an embodiment, sterilized copies need not be executed within a virtual machine, but instead, may be processed using the default file handler associated with the shell extensions. On the other hand, any digital file that is not a sterilized copy (i.e., the digital file lacks a proper digital signature) must ideally be processed within a virtual machine.

In embodiments of the invention, all of the steps of FIG. 1 or any step taken with reference to FIG. 3 may be performed in a virtual machine at any location, including but not limited to any location depicted in FIG. 2, such as cloud service 230, mail gateway 222, edge router 220, PC 224, and wireless device 226.

Benefits of Embodiments

Embodiments of the invention provide numerous benefits. The steps of FIG. 1 may be performed quickly and with little to no interaction with the user if desired. The user may remain in control of what her or she views from untrusted sources. Embodiments obviate the need to identify each and every type of file format vulnerability, as 0 day malware may be automatically removed. Sterilized copies of digital files may be safely transferred across an organization, and each recipient of the sterilized file may be assured the sterilized file is safe and trustworthy due to the digital sterilized accompanying the sterilized file.

Safe Printing

Embodiments of the invention allow a digital file to be printed in a manner designed to minimize the possibility of any malicious code contained within the digital file from spreading. Typically, a printer driver resides within the host operating system of a computer. When a digital file is printed, the host operating system uses the printer driver to capture the user's instructions on how the digital file should be printed and to translate the digital file to be printed into a format the designated printer can understand. If a digital file to be printed contains malicious code, then the malicious code may compromise the host operating system when the digital file is interpreted during the course of the printing process.

FIG. 6 is a flowchart illustrating the steps of printing a digital file safely according to an embodiment of the invention. Using the steps of FIG. 6, a digital file may be printed with little to no risk of any malicious code contained within the printed file from spreading to other files. While FIG. 6 shall be explained below with reference to printing a digital file, it is briefly noted here, and elaborated in additional detail below, that embodiments may also be used to combat the spread of malicious code through processing digital files in other ways, such as sending a facsimile of a digital file or emailing a safe copy of a digital file.

In step 610, a digital file to be printed is converted into a safe format. The purpose of performing step 610 is to convert the digital file to be printed into a format which cannot spread malicious code while being interpreted during the printing process. For example, the digital file may be transformed into a format that preserves the appearance of the digital file, but does not support the metadata and file format data structures of the original format. Malicious code is often spread using metadata and the data structures supported by certain file formats. Since the safe format does not support such metadata and file format data structures, but does allow the appearance of the digital file to be accurately described, the safe format of the digital file allows the digital file to be printed with little possibility of any malicious code contained therein from being inadvertently spread.

In one embodiment, the digital file to be printed resides within a virtual machine, such as a UCVM, when the request to print the digital file is received. When the virtual machine receives an instruction to print the digital file, step 610 is performed to convert the digital file into a safe format.

In an alternate embodiment, initially the digital file to be printed resides on a host operating system. The application through which the print command is issued causes a copy of the digital file to be transferred to a virtual machine for the performance of step 610. The virtual machine to which the digital file is transferred may be instantiated immediately prior to, and for the purposes of, performing step 610. This application may have its behavior modified with respect to how it carries out the print command using a variety of different mechanisms, including but not limited to API hooking, subclassing, and browser helper objects (BHO).

In an embodiment, step 610 may be performed as explained above with reference to step 110. The format into which the digital file is converted in step 610 may correspond to a variety of different file formats, including but not limited to a serialized representation of the digital file, a PostScript format, a Microsoft XPS file format, and an image format such as PNG or JPEG.

In an embodiment, step 610 may be performed by converting a digital file from a first format to a second format such that only a single instance of the digital file exists at any point in time. In other words, upon converting the digital file from the first format to the second format, only a single copy of the digital file exists and it is in the second format. In an alternate embodiment, step 610 may be performed by persisting a copy of the digital file in the first format after creating a copy of the digital file in the second format. In this embodiment, upon converting the digital file from the first format to the second format, two different copies of the digital file would exist—one in the first format and one in the second format. As the original format of the digital file could contain malicious code, the copy of the digital file in the original format should be treated with care if it is to be persisted, e.g., the digital file in the original format might be quarantined, analyzed for forensic purposes, and then deleted.

In an embodiment of the invention, a process executing in the virtual machine may cause a user interface to be shown to the user which allows the user to specify printing instructions for the digital file. Such printing instructions may allow the user to specify how the digital file is to be printed; non-limiting examples of such printing instructions include which printer to use, the desired number of copies, whether single or double sided printing is desired, and the like. The user interface may allow the user to specify what portion of the digital file the user wishes to print. If only a portion of the digital file is to be printed, then in an embodiment, rather than converting the entire digital file in step 610, then only that portion of the digital file desired to be printed may be converted in step 610. Note that in other embodiments, printing instructions for the digital file may be solicited from the user by a process executing from within the host operating system, as explained below.

In step 620, the converted digital file is communicated from a virtual machine to the host operating system. Embodiments may employ a variety of different file transfer mechanisms for performing step 620, such as using shared memory, a network folder, File Transfer Protocol (FTP), or direct memory access.

In step 630, the host operating system processes the converted digital file. The host operating system, in conjunction with the printer driver, may present an interface to a user that allows the user to specify printing instructions. Non-limiting examples of such printing instructions include which printer to print to, number of copies, single or double sided, and a print preview. In another embodiment of the invention, printing instructions may be obtained by a process executing within the virtual machine and subsequently forwarded to the host operating system.

The host operating system may consult policy data to determine how to print the digital file. The policy data may define any number of arbitrarily complex policies to define how digital files should be printed. For example, the policy data may instruct the host operating system to print the digital file using a default set of configurations. In this way, the digital file may be printed without providing an interface to the user that allows the user to specify printing operations to be used in printing the digital file. Such an embodiment may be advantageous if it is desired to only allow users to print to a single printer using a particular printing option. For example, an organization may allow users to print to a nearby network printer using their mobile devices, but only a single, black and white copy of a document may be printed.

As another example, the policy data may instruct the host operating system not to print the digital file. The policy data may define a blanket prohibition or one based upon the particular circumstance. For example, a particular document may not be able to be printed or a particular user may lack sufficient privileges to print. As another example, certain types of documents may be prohibited from being printed outside of normal business hours.

A variety of different types of policies may be defined in the policy data to provide an automated system for managing how digital files across an organization may be printed.

Embodiments of the invention may be implemented within a wide variety of computers or devices. For example, a non-limiting example of an embodiment is a multi-function peripheral (MFP). MFPs are often capable of sending an email and sending a facsimile of a digital file in addition to supporting printing functionalities. Embodiments of the invention may perform the steps of FIG. 6 in related to sending a facsimile or an email instead of or in addition to printing a copy of a digital file.

For example, if a user wishes to attach a digital file to an email, the steps of FIG. 6 may be performed to convert the digital file into a safe format and attach the concerted digital file to the email. As another example, if a user wishes to send a facsimile of a digital file, in an embodiment, the steps of FIG. 6 may be performed to convert the digital file into a safe format and send the facsimile using the concerted digital file.

Hardware Mechanisms

In an embodiment, the steps of FIG. 1 may be implemented on or performed by software executing on a computer system. FIG. 5 is a block diagram that illustrates a computer system 500 upon which an embodiment of the invention may be implemented. In an embodiment, computer system 500 includes processor 504, main memory 506, ROM 508, storage device 510, and communication interface 518. Computer system 500 includes at least one processor 504 for processing information. Computer system 500 also includes a main memory 506, such as a random access memory (RAM) or other dynamic storage device, for storing information and instructions to be executed by processor 504. Main memory 506 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 504. Computer system 500 further includes a read only memory (ROM) 508 or other static storage device for storing static information and instructions for processor 504. A storage device 510, such as a magnetic disk or optical disk, is provided for storing information and instructions.

Computer system 500 may be coupled to a display 512, such as a cathode ray tube (CRT), a LCD monitor, and a television set, for displaying information to a user. An input device 514, including alphanumeric and other keys, is coupled to computer system 500 for communicating information and command selections to processor 504. Other non-limiting, illustrative examples of input device 514 include a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 504 and for controlling cursor movement on display 512. While only one input device 514 is depicted in FIG. 5, embodiments of the invention may include any number of input devices 514 coupled to computer system 500.

Embodiments of the invention are related to the use of computer system 500 for implementing the techniques described herein. According to one embodiment of the invention, those techniques are performed by computer system 500 in response to processor 504 executing one or more sequences of one or more instructions contained in main memory 506. Such instructions may be read into main memory 506 from another machine-readable medium, such as storage device 510. Execution of the sequences of instructions contained in main memory 506 causes processor 504 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement embodiments of the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and software.

The term “machine-readable storage medium” as used herein refers to any tangible medium that participates in storing instructions which may be provided to processor 504 for execution. Such a medium may take many forms, including but not limited to, non-volatile media and volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 510. Volatile media includes dynamic memory, such as main memory 506.

Non-limiting, illustrative examples of machine-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, or any other medium from which a computer can read.

Various forms of machine readable media may be involved in carrying one or more sequences of one or more instructions to processor 504 for execution. For example, the instructions may initially be carried on a magnetic disk of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a network link 520 to computer system 500.

Communication interface 518 provides a two-way data communication coupling to a network link 520 that is connected to a local network. For example, communication interface 518 may be an integrated services digital network (ISDN) card or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, communication interface 518 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, communication interface 518 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

Network link 520 typically provides data communication through one or more networks to other data devices. For example, network link 520 may provide a connection through a local network to a host computer or to data equipment operated by an Internet Service Provider (ISP).

Computer system 500 can send messages and receive data, including program code, through the network(s), network link 520 and communication interface 518. For example, a server might transmit a requested code for an application program through the Internet, a local ISP, a local network, subsequently to communication interface 518. The received code may be executed by processor 504 as it is received, and/or stored in storage device 510, or other non-volatile storage for later execution.

In the foregoing specification, embodiments of the invention have been described with reference to numerous specific details that may vary from implementation to implementation. Thus, the sole and exclusive indicator of what is the invention, and is intended by the applicants to be the invention, is the set of claims that issue from this application, in the specific form in which such claims issue, including any subsequent correction. Any definitions expressly set forth herein for terms contained in such claims shall govern the meaning of such terms as used in the claims. Hence, no limitation, element, property, feature, advantage or attribute that is not expressly recited in a claim should limit the scope of such claim in any way. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. 

What is claimed is:
 1. One or more non-transitory computer-readable storage mediums storing one or more sequences of instructions, which when executed by one or more processors, cause: processing a digital file in a manner designed to minimize exposure of any malicious code contained within the digital file to a host operating system by performing: upon the host operating system receiving an instruction to print or digitally transfer at least a portion of the digital file stored in an original file format by the host operating system, the host operating system automatically causing one or more virtual machines, executing on the same physical machine as the host operating system, to convert at least the portion of the digital file from the original file format to a different file format within the one or more virtual machines, wherein the different file format preserves a visual presentation of the digital file without supporting metadata or file format data structures of the original file format; and the one or more virtual machines instructing the host operating system to print or digitally transfer the portion of the digital file in the different file format.
 2. The one or more non-transitory computer-readable storage mediums of claim 1, wherein the different file format is a serialized representation of the digital file.
 3. The one or more non-transitory computer-readable storage mediums of claim 1, wherein the different file format is a PostScript format, a Microsoft XPS file format, or an image format.
 4. The one or more non-transitory computer-readable storage mediums of claim 1, wherein the one or more virtual machines are instantiated in response to receiving a request to print or digitally transfer the portion of the digital file.
 5. The one or more non-transitory computer-readable storage mediums of claim 1, wherein the one or more virtual machines do not comprise a printer driver used to print the digital file, and wherein execution of the one or more sequences of instructions further causes: the host operating system presenting an interface to a user which allows the user to specify printing instructions.
 6. The one or more non-transitory computer-readable storage mediums of claim 1, wherein execution of the one or more sequences of instructions further causes: the host operating system consulting policy data to determine how to print or digitally transfer the portion of the digital file.
 7. The one or more non-transitory computer-readable storage mediums of claim 1, wherein execution of the one or more sequences of instructions further causes: in response to the host operating system consulting policy data to determine how to print or digitally transfer the portion of the digital file in the different file format; the host operating system causing the portion of the digital file to be printed or digitally transferred without providing an interface to the user that allows the user to specify options to be used in printing or digitally transferring the portion of the digital file in the different file format.
 8. The one or more non-transitory computer-readable storage mediums of claim 1, wherein execution of the one or more sequences of instructions further causes: in response to the host operating system consulting policy data to determine how to print or digitally transfer the portion of the digital file in the different format; the host operating system determining that the digital file should not be printed or digitally transferred.
 9. The one or more non-transitory computer-readable storage mediums of claim 1, wherein the one or more computer-readable storage mediums are comprised within a multi-functional peripheral.
 10. The one or more non-transitory computer-readable storage mediums of claim 1, wherein the one or more virtual machines converting at least the portion of the digital file from the original file format to the different file format within the virtual machine comprises: a first virtual machine converting the portion of the digital file from the original file format to an intermediate file format; and a second virtual machine converting the portion of the digital file from the intermediate file format to the different file format, wherein the intermediate file format is not the same file format as the original file format or the different file format.
 11. The one or more non-transitory computer-readable storage mediums of claim 10, wherein the first virtual machine is different than the second virtual machine.
 12. The one or more non-transitory computer-readable storage mediums of claim 10, wherein the first virtual machine is the same as the second virtual machine.
 13. The one or more non-transitory computer-readable storage mediums of claim 1, wherein the portion of the digital file in the different file format is the entire digital file in the different file format.
 14. The one or more non-transitory computer-readable storage mediums of claim 1, wherein digitally transferring the digital file includes emailing the digital file, sending a facsimile of the digital file, or saving a copy of the digital file on a network.
 15. The one or more non-transitory computer-readable storage mediums of claim 1, wherein the one or more virtual machines solicit instructions from the user on how the portion of the digital file should be printed or digitally transferred.
 16. The one or more non-transitory computer-readable storage mediums of claim 1, wherein an instance of the digital file in the original file format is maintained after the digital file has been converted into the different file format.
 17. An apparatus, comprising: one or more processors; and one or more non-transitory computer-readable storage mediums storing one or more sequences of instructions, which when executed by the one or more processors, cause: processing a digital file in a manner designed to minimize exposure of any malicious code contained within the digital file to a host operating system by performing: upon the host operating system receiving an instruction to print or digitally transfer at least a portion of the digital file stored in an original file format by the host operating system, the host operating system automatically causing one or more virtual machines, executing on the same physical machine as the host operating system, to convert at least the portion of the digital file from the original file format to a different file format within the one or more virtual machines, wherein the different file format preserves a visual presentation of the digital file without supporting metadata or file format data structures of the original file format; and the one or more virtual machines instructing the host operating system to print or digitally transfer the portion of the digital file in the different file format.
 18. The apparatus of claim 17, wherein the one or more virtual machines converting at least the portion of the digital file from the original file format to the different file format within the virtual machine comprises: a first virtual machine converting the portion of the digital file from the original file format to an intermediate file format; and a second virtual machine converting the portion of the digital file from the intermediate file format to the different file format, wherein the intermediate file format is not the same format as the original file format or the different file format.
 19. The apparatus of claim 17, wherein digitally transferring the digital file includes emailing the digital file, sending a facsimile of the digital file, or saving a copy of the digital file on a network.
 20. A method for processing a digital file in a manner designed to minimize exposure of any malicious code contained within the digital file to a host operating system, comprising: upon the host operating system receiving an instruction to print or digitally transfer at least a portion of the digital file stored in an original file format by the host operating system, the host operating system automatically causing one or more virtual machines, executing on the same physical machine as the host operating system, to convert at least the portion of the digital file from the original file format to a different file format within the one or more virtual machines, wherein the different file format preserves a visual presentation of the digital file without supporting metadata or file format data structures of the original format; and the one or more virtual machines instructing the host operating system to print or digitally transfer the portion of the digital file in the different file format. 